Help for Performance Settings

Use this form to control the performance of your server.

Performance Settings

You can control the performance of your server by setting a range for active or available threads, setting an expiration time for idle threads, and assigning a priority class to the server.

By having a pool of threads available to your server, you can reduce the number of times your server needs to start and close new threads. Each time your server receives a request from a client, it uses one or two processes, called threads, to perform the requested action. The server first checks to see if any threads are available. If so, the server uses available threads to process the request. If not, the server has to start new threads. When the request finishes, the threads it was using become idle. As long as idle threads do not expire, they are available for the server to use again.

To change the performance settings:

1. Fill in the following fields:
• Minimum number of active threads - the minimum number of threads that you want the server to either be using or have available to use. The server will not close available threads below this minimum even if the threads are idle. Generally, the more requests your server receives, and the more power your machine has, the higher the value you should use for this directive.
• Maximum number of active threads - the maximum number of threads that you want to have active at one time. If the maximum is reached, the server holds new requests until another request finishes and threads become available. Generally, the more requests your server receives, and the more power your machine has, the higher the value you should use for this directive.
• Length of time to keep idle threads available - the amount of time the server should keep an idle thread available. A thread becomes idle after the last request to use it completes. If the number of threads already available or active is greater than the value you specified for Minimum number of active threads, and the server does not use the thread again within the specified time, the server closes the idle thread. Specify a time using any combination of hours, mins (minutes), and secs (seconds). If you do not want the server to close any idle threads, specify forever as the value.

    Examples:  30 secs
               15 mins
               20 mins 30 secs

• Server priority - the priority class you want the server to have. The operating system uses priority classes to determine which processes have priority over others. Valid values are:
  • 0 - no priority
  • 1 - maximum priority as a normal process
  • 2 - maximum priority as a foreground process
2. If you want to use the changes you make to the form, select the Apply button. If you want to go back to the values that were on the form before you made changes, select the Reset button.